Add the portal-reader ClusterRole addon#41
Merged
Conversation
portal (the ops portal) reaches managed clusters with its per-account spoke IAM role, mapped to the "portal-reader" Kubernetes group via an EKS access entry (landing-zone fleet/aws/cluster-stack). This binds that group to the minimal read portal needs: the eks-agent-platform Tenant/Platform CRs (its tenant-inventory watcher) + nodes (best-effort node count in the connection test). No Secrets, no workloads — the least-privilege replacement for the broad AmazonEKSAdminViewPolicy the access entry would otherwise carry. A pure-Kustomize bootstrap addon (base + dev/staging/production overlays) applied to every cluster by addons-bootstrap-kustomize, so each spoke self-reconciles it via its spoke-local ArgoCD.
CI Results
All validations passed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pairs with landing-zone#51 (nanohype/portal#49). portal reaches managed clusters with its per-account spoke IAM role, mapped to the
portal-readerKubernetes group via an EKS access entry. This binds that group to the minimal read portal needs — the eks-agent-platformTenant/PlatformCRs (its tenant-inventory watcher) + nodes (best-effort node count). No Secrets, no workloads — the least-privilege replacement for the broadAmazonEKSAdminViewPolicythe access entry would otherwise carry.A pure-Kustomize bootstrap addon (base + dev/staging/production overlays) applied to every cluster by
addons-bootstrap-kustomize, so each spoke self-reconciles it via spoke-local ArgoCD.Validated:
task validate(yamllint + kustomize build all overlays).